chore: add firstlook PR-author reputation check#121
Merged
Conversation
Runs on every PR open/reopen/synchronize against getagentseal/firstlook and fails the check when the author's score is 'unknown' (new or untracked accounts). Skips bot accounts so dependabot and renovate pass through. This screens the same drive-by pattern that landed in PR #118 (octo-patch, fresh automation account) without requiring a manual tier check on every submission.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a GitHub Actions workflow that runs `getagentseal/firstlook@main` on every pull_request open/reopen/synchronize. The action assigns a reputation score to the PR author; this config fails the check when the score is `unknown` so drive-by PRs from freshly-minted or untracked accounts need manual review before they can be merged.
Rules for this workflow:
Context: PR #118 earlier today was a drive-by from a 42-day-old automation account with 928 repos. Manually spotting that takes time. This screens it at the workflow level instead.